Repository navigation
Document native Server conformance entry points - #376
Merged
Merged
Conversation
|
rmcdaniel
commented
Nov 13, 2026
rmcdaniel
left a comment
Member
Author
There was a problem hiding this comment.
Independent CLI doc review: PASS at 3dee9de43c0402c1a6851df946115e98630b0cf8, checked against Server main f315a015e319191f9b93443cb8ea2ff9a541ab12. No blocking findings in this diff.
- The native corpus and Compose dispatch inputs are
native_imageandserver_image. Their tag/index requirements match the linked publication runbook and admission helper. - Compose has exactly amd64/arm64 × local/production. The selection manifest requires one corpus receipt plus four cell receipts; finalization requires successful body and cleanup, verified absence, and matching provider run identity. The new text correctly refuses to treat a passing body or source-built PR image as published qualification.
- The activity and child fixture sets each contain all nine PHP/Python/Rust directions. Timer fixtures cover all three workflow languages. The profile selector includes the named signal, query, update and failure variants, with embedded transport marked inapplicable.
sdk-direction-lanes.shrequires three arguments andRESOURCE_SCOPE. The owning workflow supplies two native URLs backed by distinct databases, prepares adapters, and runs each profile's cleanup.
One nonblocking upstream documentation drift: the linked Server SDK README at line 37 still shows the two-argument lane invocation and says one native server. This PR's three-argument command is correct; Server's README should be aligned separately.
Source inspection only. No code changes, CI dispatches or runtime experiments performed. General retains merge and main verification.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



The shared conformance runbook still sends native Server release readers through PHP-hosted probes. Document the existing published-native corpus and four-cell Compose checks, their receipt requirements, and the authored PHP/Python/Rust direction profiles.
Separate frozen PHP reference behavior, source-built targets and historical SDK tuples from published native acceptance. Include the current lane wrapper's two isolated native URLs and link the owning preparation and cleanup instructions.
Refs #122. This changes instructions only; no runtime experiment or publication is claimed. Verified the commands, workflow inputs, matrix cells and profile variants against current Server source;
git diff --checkpasses. Normal repository checks will run on this PR.